Flip deprecation in XmlNode methods - #13032

Closing this — the record-accessor naming (name(), value(), children()) is intentional and consistent with the Maven 4 API design for immutable value types.

See the detailed rationale on the issue: #11582 (comment)

In short: the noun-accessor pattern for immutable types is well established in the JDK itself (since Java 8/9, well before records), and XmlNode is an immutable value type by contract. Flipping the deprecation would break users who already migrated following the existing deprecation guidance, and create inconsistency with PathType, Lifecycle.Phase, OsService, CIInfo which all use the same pattern.